
THIS IS A TEMPORARY FILE	

Mobile IP Numbers - per [RFC2002]

(last updated 2001 August 31)

The document "IP Mobility Support" [RFC 2002] specifies some message
types and extensibility fields.


Message Format and Protocol Extensibility
-----------------------------------------

Mobile IP defines a set of new control messages, sent with UDP [17]
using well-known port number 434.  Currently, the following two
message types are defined:

   1  Registration Request
   3  Registration Reply


Two separately maintained sets of numbering spaces, from which
Extension Type values are allocated, are used in Mobile IP:

The first set consists of those Extensions which may appear only
in Mobile IP control messages (those sent to and from UDP port
number 434).  Currently, the following Types are defined for
Extensions appearing in Mobile IP control messages:

Value  Name							Reference
-----  --------------------------------------			---------

   32  Mobile-Home Authentication                               [RFCXXXX]
   33  Mobile-Foreign Authentication                            [RFCXXXX]
   34  Foreign-Home Authentication                              [RFCXXXX]
   36  Generalized Mobile IP Authentication			[RFC3012]
   38  Critical Vendor/Organization Specific Extension(CVSE)    [RFC3025]
  128  Deprecated (2001 Aug 31)
  129  Traversal Extension		 		        [RFC2356]
  130  Encapsulating Delivery Style Extension			[RFC3024]
  131  Mobile Node NAI						[RFC2794]
  134  Normal Vendor/Organization Specific Extension (NVSE)	[RFC3025]


The second set consists of those extensions which may appear only
in ICMP Router Discovery messages [4].  Currently, Mobile IP
defines the following Types for Extensions appearing in ICMP
Router Discovery messages:

Value  Name							Reference
-----  ------------------------------------------		---------

    0  One-byte Padding (encoded with no Length nor Data field) [RFCXXXX]
   16  Mobility Agent Advertisement                             [RFCXXXX]
   19  Prefix-Lengths                                           [RFCXXXX]
   24  Challenge Extension					[RFC3012]
  132  MN-FA Challenge Extension				[RFC3012]
          

Due to the separation (orthogonality) of these sets, it is
conceivable that two Extensions that are defined at a later date
could have identical Type values, so long as one of the Extensions
may be used only in Mobile IP control messages and the other may be
used only in ICMP Router Discovery messages.

When an Extension numbered in either of these sets within the range
0 through 127 is encountered but not recognized, the message
containing that Extension MUST be silently discarded.  When an Extension
numbered in the range 128 through 255 is encountered which is not
recognized, that particular Extension is ignored, but the rest of
the Extensions and message data MUST still be processed.  The


Code Values for Mobile IP Registration Reply Messages
-----------------------------------------------------
         0-8        Success Codes
         9-63       No allocation guidelines currently exist
         64-128     Error Codes from the Foreign Agent
         128-192    Error Codes from the Home Agent
         193-255    No allocation guidelines currently exist


The following values are defined for use within the Code field.
  Registration successful:

        0 registration accepted
        1 registration accepted, but simultaneous mobility
          bindings unsupported

  Registration denied by the foreign agent:

       64 reason unspecified
       65 administratively prohibited
       66 insufficient resources
       67 mobile node failed authentication	        [RFC2002,RFC3012]
       68 home agent failed authentication
       69 requested Lifetime too long
       70 poorly formed Request
       71 poorly formed Reply
       72 requested encapsulation unavailable
       73 requested Van Jacobson compression unavailable
       74 request reverse tunnel unavailable			[RFC3024]
       75 reverse runnel is mandatory and 'T' bit not set	[RFC3024]
       76 mobile node too distant				[RFC3024]
       79 delivery style not supported				[RFC3024]
       80 home network unreachable (ICMP error received)
       81 home agent host unreachable (ICMP error received)
       82 home agent port unreachable (ICMP error received)
       88 home agent unreachable (other ICMP error received)
    89-95 unassigned
       96 nonzero_homeaddr_reqd					[RFC2794]
       97 missing_nai						[RFC2794]
       98 missing_home_agent					[RFC2794]
       99 missing_homeaddr					[RFC2794]
      100 ERROR-FA-1						[RFC3025]
      101 ERROR-FA-2						[RFC3025]
  102-103 unassigned				
      104 unknown_challenge					[RFC3012]
      105 missing_challenge					[RFC3012]
      106 stale_challenge					[RFC3012]


   Registration denied by the home agent:

      128 reason unspecified
      129 administratively prohibited
      130 insufficient resources
      131 mobile node failed authentication
      132 foreign agent failed authentication
      133 registration Identification mismatch
      134 poorly formed Request
      135 too many simultaneous mobility bindings
      136 unknown home agent address			   
      137 request reverse tunnel unavailable                    [RFC3024]
      138 reverse runnel is mandatory and 'T' bit not set	[RFC3024]
      139 requested encapsulation unavailable			[RFC3024]
      140 ERROR-HA-1						[RFC3025]
      141 ERROR-HA-2						[RFC3025]
	

SPI Values for the Mobile IP Reserved SPIs
------------------------------------------
	0 Reserved						[RFC3012]
        1 Reserved						[RFC3012]
        2 CHAP							[RFC3012]

Generalized Authentication Extension - Subtypes

	1 MN-AAA Authentication subtype				[RFC3012]


PEOPLE
------

[Solomon] Jim Solomon <solomon@comm.mot.com>, December 1997.

REFERENCES
---------- 

[RFC2356] G. Montenegro and V. Gupta, "Sun's SKIP Firewall Traversal 
          for Mobile IP", RFC 2356, June 1998.

[RFC2794] Calhoun, P. and C. Perkins, "Mobile IP Network Access
          Identifier Extension for IPv4", RFC 2794, March 2000.

[RFC3012] C. Perkins and P. Calhoun, "Mobile IPv4 Challenge/Response 
          Extensions", RFC 3012, November 2000.

[RFC3024] G. Montenegro, "Reverse Tunneling for Mobile IP, revised",
          RFC 3024, January 2001.

[RFCXXXX] 

[]















